Skip to content

Accept nullable service_name on SP configuration push#606

Open
kayjoosten wants to merge 1 commit into
mainfrom
feature/issue-589-service-name-config
Open

Accept nullable service_name on SP configuration push#606
kayjoosten wants to merge 1 commit into
mainfrom
feature/issue-589-service-name-config

Conversation

@kayjoosten

Copy link
Copy Markdown
Contributor

Gateway needs a display name to show during authentication (Gateway #624 already reads a service_name key from the pushed SP config JSON blob). Middleware was rejecting any config push containing that key, since ServiceProviderConfigurationValidator whitelists the exact set of allowed keys per service provider entry.

Add service_name as an optional, nullable string: omitted keys default to null before the key-set check runs, so existing config pushes that don't set it keep working unchanged.

Refs #589

@kayjoosten kayjoosten requested a review from johanib July 10, 2026 09:39
Gateway now expects an optional service_name in pushed SP
configuration so it can display a friendly name during
authentication. Middleware still rejected that key because the
validator only allowed the older field set, and fresh CI installs had
become flaky because phpcpd-shim was fetched from a dead upstream Git
host.

Allow service_name as an optional nullable field in the service
provider validator and add regression coverage for valid and invalid
configurations. Replace the dead phpcpd shim with the maintained
phpcpd-next package so fresh installs keep working reliably.

Resolves: #589
@kayjoosten kayjoosten force-pushed the feature/issue-589-service-name-config branch from 3ef68b6 to 49d2b19 Compare July 10, 2026 11:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant